Skip to content

Add one-shot workflow to close the Comunity Release milestone (issue 13) - #14

Closed
QuasarAppCI wants to merge 1 commit into
QuasarApp:mainfrom
QuasarAppCI:task_13
Closed

QuasarAppCI wants to merge 1 commit into
QuasarApp:mainfrom
QuasarAppCI:task_13

Conversation

@QuasarAppCI

Copy link
Copy Markdown
Member

Task issue_13 "Comunity Release"

Issue #13 asks to close the "Comunity Release" milestone with all its issues.
The QuasarAppCI bot account only has read (pull) access on this repository
(no triage / maintain / push), so it cannot close issues or manage labels
directly:

  • GraphQL closeIssue -> "QuasarAppCI does not have the correct permissions to execute CloseIssue"
  • REST PATCH /issues/{n} (state=closed) -> 403 "Must have admin rights to Repository"

This PR adds a one-shot, manually triggered workflow
.github/workflows/close-community-release.yml that runs with the repository
GITHUB_TOKEN (issues: write, milestones: write) and:

  1. prints the effective token permissions (diagnostic),
  2. closes every open issue of milestone Improve rust speed #1 ("Comunity Release": currently Update readme #8, Change Liense to LGPLv3 #9, Implement GitHub Page #12, Comunity Release #13 — Implement Github Actions #7 was already closed),
  3. closes milestone Improve rust speed #1 itself,
  4. prints the final state of all milestone issues and the milestone.

Usage (maintainer):

  1. Merge this PR.
  2. Actions -> "Close Community Release Milestone" -> Run workflow.
  3. Check the final-state log — milestone Improve rust speed #1 and all its issues are closed.

The workflow is workflow_dispatch-only (never runs automatically) and can be
deleted from the repository after the first successful run.

Alternative: grant the QuasarAppCI account maintain permission on the
repository and the agent will close the issues and milestone directly in the
next cycle (no workflow needed).

@QuasarAppCI QuasarAppCI mentioned this pull request Oct 13, 2026
@EndrII

EndrII commented Oct 13, 2026

Copy link
Copy Markdown
Member

@QuasarAppCI no - release means close all issues in milistone. This workflow is not required.

@EndrII EndrII closed this Oct 13, 2026
@QuasarAppCI
QuasarAppCI deleted the task_13 branch October 13, 2026 16:34
@QuasarAppCI

Copy link
Copy Markdown
Member Author

Understood — the workflow is not required; PR closed (not merged) and the orphaned task_13 branch deleted.

One factual note: the QuasarAppCI account currently has read-only (pull) access on this repository, so it cannot close issues or manage labels (verified: GraphQL CloseIssue denied; REST PATCH /issues -> 403 "Must have admin rights to Repository"; label API denied).

Please pick one:

  1. close the remaining milestone items directly: issues Update readme #8, Change Liense to LGPLv3 #9, Implement GitHub Page #12, Comunity Release #13 + milestone Improve rust speed #1 "Comunity Release" (Implement Github Actions #7 is already closed), or
  2. grant the QuasarAppCI account maintain permission — I will close them all in the next cycle.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants